Task: Verify the software unit design
This task verifies that the software unit is compliant with the hardware software interface, the software unit specification and coding guidelines. It shall also be compatible with the target hardware and a full traceability coverage back to software safety requirements and the software architecture.
Purpose
To ensure that the software component can work with the HW and is developed according to the guidelines.
Relationships
Main Description

Verification that the software unit is compliant with the hardware/software interface, the software unit specification and coding guidelines. It shall also be compatible with the target hardware and a full traceability coverage back to software safety requirements and the software architecture.

Methods for the verification of the software unit design and implementation are highly dependent on upon the ASIL of the item/element being developed, these methods with there applicability to an items ASIL level are detailed below.

Walk througha is highly recommended for items of ASIL A and recommended for items of ASIL B, with an unbiased opinion on its usage for items of ASIL C or D

Inspectiona is highly recommended for items of ASIL B, C or D and recommended for items of ASIL A

Semi-formal verification is highly recommended for items of ASIL C or D  and recommended for items of ASIL A or B

Formal verification is recommended for items of ASIL C or D, with an unbiased opinion on its usage for items of ASIL A or B

Control flow analysis b,c is highly recommended for items of ASIL C or D and recommended for items of ASIL A or B

Data flow analysis b,c is highly recommended for items of ASIL C or D and recommended for items of ASIL A or B

Static code analysis is highly recommended for items of ASIL B, C or D and recommended for items of ASIL A

Semantic code analysis d is recommended for items of all ASIL level

Notes

a:- In the case of model-based software development the software unit specification design and implementation can be verified at the model level.

b:- Can be applied at the source code level, these methods are applicable to model based and manual code development

c:- These methods can be considered to be part of Formal Verification, Static Code Analysis and Semantic Code Analysis

d:- Is used for mathematical analysis of source code by use of an abstract representation of possible values for the variables. For this it is not required to translate and execute the source code.

This information is a summary of the information taken from ISO 26262 vol 6 clause 8.4.5 Table 9- Methods for the verification of software unit design and implementation

If using model based techniques. Model walkthrough and inspection are valid ways of verifying the software unit specification. If a model based approach is used for automatic code generation it is possible to replace the informal methods of code inspection and walkthrough by automated methods and techniques.

If the code is to be included as part of a production release it shall be verified that it contains all the specified functions. If other functions are included it shall be ensured that these cannot impair the compliance of the software with the software safety requirements.

Code used for other functions such as development or debugging can only be included if developed and verified to the same safety standards as the rest of the code. Removal of the code is deemed to be a change, but deactivation of these functions is an acceptable means of compliance.




 

Properties
Predecessor
Multiple Occurrences
Event Driven
Ongoing
Optional
PlannedYes
Repeatable
Key Considerations

Practices applicable to verify the software unit design are

More Information